System and method for modification management of a configuration system

ABSTRACT

A modification management system for a configuration system, includes, not limited to a comparator, a record generator and a link generator implemented in one or more processors. The comparator is configured to determine if a first modification item in a first instruction file is modified. The record generator is configured to create a first record and to store the first modification item in a first record when the first modification item is determined, by the comparator, to be modified. The link generator configured to generate a first link between the first record and the first instruction file, wherein the first instruction file is configured to define at least one modification item for the configuration system.

TECHNICAL FIELD

The disclosure generally relates to a field of industrial automation foran industrial plant. In particular, the disclosure relates to amodification system which may be used for one or more configurationsystems of an industrial plant.

BACKGROUND

An industrial automation system, which is used for an industrial processplant, includes different types of systems. The different types systemsare for different purposes and there may be more than one system foreach type. Examples of those purposes are process control and safetycontrol. Each type of the systems may be configured or set up in anengineering phase, then used in an operation phase and updated in amaintenance phase.

At each phase, engineering, operation and maintenance, each system mayhave separate tool and database. The tool may include, but not limitedto, a computing device installed with a software and used to completetask in each phase. In an example, a configuration software is a toolwhich is used to complete a task to define a control logic for acontroller in the plant.

A user need to find use each separate tool to identify a history ofchanges for a hardware component, such a field device or equipment, whenthere is a problem with the hardware component. From the identifiedhistory of changes, the user can trace the changes in the history tosolve the problem.

In a typical plant, a first engineer submits a change request forapproval before the change is performed. The change may include, notlimited to, allocating an identification tag to a hardware component,define parameters in a control logic. A second engineer performs thechange when the approval has been given for the change request. A thirdengineer then checks the system to confirm that the change has beencompleted.

A lot of manual efforts and logistics are needed to keep records ofchange requests and completion of the change requests. More manualeffort and time are need to check and determine if the change requestshave been completed. In one change request, there may be a plurality ofmodification items, changes which are required. This is especially foran industrial automation system which includes, not limited to, acomplex network of components. Each component may have a plurality ofparameters and corresponding values.

SUMMARY

A modification management system for a configuration system, includes,not limited to a comparator, a record generator and a link generatorimplemented in one or more processors. The comparator is configured todetermine if a first modification item in a first instruction file ismodified. The record generator is configured to create a first recordand to store the first modification item in a first record when thefirst modification item is determined, by the comparator, to bemodified. The link generator configured to generate a first link betweenthe first record and the first instruction file, wherein the firstinstruction file is configured to define at least one modification itemfor the configuration system.

BRIEF DESCRIPTION OF DRAWINGS

FIG. 1 is a block diagram of an overview of a modification managementsystem for a configuration system of an industrial plant according tosome embodiments of the invention.

FIG. 2 is a diagram of a modification management system according tosome embodiments of the invention.

FIG. 3 is an illustration of an application being activated when anaccess link is selected according to some embodiments of the invention.

FIG. 4 is an illustration of a plurality of links being generatedaccording to some embodiments of the invention.

FIG. 5 is a table of records, links and instruction files according tosome embodiments of the invention.

FIGS. 6A and 6B are workflows of the modification management systemaccording to some embodiments of the invention.

DETAILED DESCRIPTIONS

FIG. 1 illustrates a modification management system 100 for aconfiguration system 10 of an industrial plant. The configuration system10 may include, but not limited to, a plurality of configuration systems10 for different types of systems used in the industrial plant. Thedifferent types of systems are used for different purposes in the plant.The plant includes, not limited to hardware, field devices andequipment, used for one or more industrial processes.

An instruction file 12 is provided to the modification management system100 in FIG. 2. The instruction file 12 may include, but not limited to,a modification item 14. The modification item 14 is related to theconfiguration system 10. A comparator 16 is configured to determine ifthe modification item 14 being modified. A record generator 18 isconfigured to create a record 20 and store the modification item 14 inthe record 20 when the modification item 14 is determined to bemodified. A link generator 22 is configured to generate a link 24between the record 20 and the instruction file 12 when the modificationitem 14 has been modified.

A modification item 14 defines a modification which is required for aconfiguration system. The modification may be a result of change indesign or specifications of the plant. A change in component, equipmentor field device or process conditions may require a modification. Themodification is required to maintain and update the configurationsystem. This is to ensure that the plant is updated and operationalaccording to an updated design or specifications.

The modification item 14 in FIG. 3 may include, but not limited to, anaccess link 32 to access an item 33 using a tool 34 such as anapplication. For an item 33 which is related to parameters of a plantconfiguration, the application is an editor. For an item 33 which isrelated to a user manual, the application is a word processor for theuser manual. The item 33 is a file which may include, but not limitedto, configuration data and information. An example of information isdescription in a user manual related to the configuration system. Theapplication 34 is activated and the item 33 is accessed when themodification management system 100 receives a user input to select theaccess link 32. The user can view or edit the item 33 using theapplication when the application is activated.

The modification management system 100 receives user input to check-outthe instruction file 12 at a check-out event. The instruction file 12which is in a check-out state is disabled for editing to add or changethe modification item 14. In the check-out state, the user modifies themodification item 14. The modification item 14 is modified when the userselects an access link 32.

The modification system 100 receives a user input to check-in theinstruction file 12 at a check-in event.

The comparator 16 is configured to determine if the modification item 14being modified when the instruction file 12 is in a check-in state. Thecomparator 16 reads the modification item 14 at the check-in state andat the check-out state. Then the comparator 16 compares if themodification item 14 is different at the check-in state and at thecheck-out state. Finally, the comparator 16 determines the modificationitem 14 has been modified when the modification item 14 at the check-outstate is different at the check-in state.

The record generator 18 is configured to create a new record 20 when thecomparator determines that the modification item 14 has been modified.The modification item 14 being modified is stored to the record 20. Therecord 20 has the modification item 14 being modified in a periodbetween the check-out event and the check-in event.

The link generator 22 then generates the link 24 between the record 20and the instruction file 12. The link 24 is a relationship indicatorwhich indicates that there record 20 is related to the instruction file12.

An instruction file 12 is provided to the modification management system100. The instruction file 12 may include, but not limited to, aplurality modification items 14. The plurality of modification items 14is related to the configuration system 10. A comparator 16 is configuredto determine if the plurality of modification items 14 being modified. Arecord generator 18 is configured to create a record 20 and store theplurality of modification items 14 when the plurality of themodification items 14 being determined to be modified. A link generator22 is configured to generate a link 24 between the record 20 and theinstruction file 12 when the plurality of modification items 14 beingmodified.

A modification item 14 is a definition of a modification for theconfiguration system 10. The modification may be a result of change indesign or specifications of the plant. A change in component, equipmentor field device or process conditions may require a modification. Themodification is required to maintain and update the configurationsystem. This is to ensure that the plant is updated and operationalaccording to an updated design or specifications.

Each of the plurality of modification items 14 may include, but notlimited to, an access link 32 to access an item 33 using a tool 34, suchas an application. The item 33 is a folder which may include, but notlimited to, configuration data and information. An example ofinformation is description in a user manual related to the configurationsystem. The application 34 is activated and the item 33 is accessed whenthe management system 100 receives a user input to select the accesslink 32. The user can view or edit the item 33 using the applicationwhen the application is activated.

The modification management system 100 receives user input to check-outthe instruction file 12 at a check-out event. The instruction file 12which is in a check-out state is disabled for editing to add or changethe plurality of modification items 14. In the check-out state, the usermodifies the plurality of modification items 14. Each of the pluralityof modification items 14 is modified when the user selects an accesslink 32.

The modification system 100 receives a user input to check-in theinstruction file 12 at a check-in event. An additional user input isreceived to check-in at least of the plurality of modification items 14.

The comparator 16 is configured to determine if the each of theplurality of modification items 14 being modified when the instructionfile 12 is in a check-in state. For each of the plurality ofmodification items 14, the comparator 16 reads the modification item 14at the check-in state and at the check-out state. Then the comparator 16compares if the modification item 14 is different at the check-in stateand at the check-out state. Finally, the comparator 16 determines themodification item 14 has been modified when the modification item 14 atthe check-out state is different at the check-in state.

The record generator 18 is configured to create a new record 20 when thecomparator determines that at least of the plurality of modificationitems 14 being modified. The at least of the plurality of modificationitems 14 being modified are stored to the record 20. The record 20 hasat least of the plurality of modification items 14 being modified in aperiod between the check-out event and the check-in event.

The link generator 22 is configured to identify the instruction file 12of the plurality of modification items 14. The link generator 22 thengenerates the link 24 between the record 20 and the instruction file 12.The link 24 is a relationship indicator which indicates that thererecord 20 is related to the instruction file 12.

The instruction file 12 has a plurality of check-out events and check-inevents when the instruction file 12 is modified at a plurality ofperiods. The plurality of modification items 14 in the instruction file12 are modified during periods of the different check-in and check-outinstances. FIG. 4 illustrates a plurality of records 20 and links 24being generated, each record 20 for each period and each link 24 isbetween the instruction file 12 and one of the plurality of records 20.

According to another embodiment of the invention, the instruction file12 may include, but not limited to, a plurality of instruction files 12.Each of the plurality of instruction files 12 has a plurality ofmodification items 14. Each of the modification item 14 may include, butnot limited to, an access link 32 to access an item 33 using a tool 34,such as an application. The item 33 is a folder which may include, butnot limited to, configuration data and information. An example ofinformation is description in a user manual related to the configurationsystem. The application 34 is activated and the item 33 is accessed whenthe management system 100 receives a user input. The user can view oredit the item 33 using the application when the application isactivated.

At a check-out event, user input is received to check-out at least oneof the plurality of instructions files 12. The plurality of instructionfiles 12 is provided to the display in a list. A user input is receivedto determine the at least one of the plurality of instruction files 12being check-out. The at least one of the plurality of instruction files12 which is in a check-out state is disabled for editing to add orchange the plurality of modification items 14. Additional user input isreceived to check-out at least one of the plurality of modificationitems 14 based on a predefined level of granularity.

In the check-out state, the user modifies the plurality of modificationitems 14. Each of the plurality of modification items 14 is modifiedwhen the user selects an access link 32.

The modification system 100 receives user input to check-in at least oneof the plurality of instruction files 12 at a check-in event. Additionaluser input is received to check-in at least of the plurality ofmodification items 14 based on a predefined level of granularity.

A checkbox 36 is provided next to each of the plurality of instructionfiles 12 and each of the plurality of modification items 14. The userinput is in a form of a check in the checkbox 36.

The comparator 16 is configured to determine if the each of theplurality of modification items 14 being modified when the at least oneof the plurality of instruction files 12 and at least one of theplurality of modification items are in a check-in state. For each of theplurality of modification items 14 in the check-in state, the comparator16 reads the modification item 14 at the check-in state and at thecheck-out state. Then the comparator 16 compares if the modificationitem 14 is different at the check-in state and at the check-out state.Finally, the comparator 16 determines the modification item 14 has beenmodified when the modification item 14 at the check-out state isdifferent at the check-in state.

The record generator 18 is configured to create a new record 20 when thecomparator determines that at least of the plurality of modificationitems 14 being modified. The at least of the plurality of modificationitems 14 being modified are stored to the record 20. The record 20 hasat least one of the plurality of modification items 14 being modified ina period between the check-out event and the check-in event.

The link generator 22 is configured to identify the instruction file 12of the plurality of modification items 14 in the record 20. The linkgenerator 22 then generates the link 24 between the record 20 and theinstruction file 12. The link 24 is a relationship indicator whichindicates that there record 20 is related to the instruction file 12.

The instruction file 12 has a plurality of check-out events and check-inevents when the instruction file 12 is modified at a plurality ofperiods. The plurality of modification items 14 in the instruction file12 are modified during periods of the different check-in and check-outinstances. There are a plurality of records 20 and links generated, eachrecord for each period and each link is between the instruction file 12and one of the plurality of records. A first check-in event is a firstinstance. The next check-in event, a second check-in event, is a secondinstance. The first instance and the second instance are different andseparate events.

In an embodiment, a plurality of instruction files 12 are check-out andthe record 20 includes a plurality of modification items 14 from theplurality of instruction files 12. The link generates a plurality oflinks 24, each link between the record 20 and each of the plurality ofinstruction files 12.

The instruction file 12 is being configured for the configuration system10 by manual effort or using a computing device with a software. Theinstruction file may include, but not limited to, an identifier which isunique to the instruction file 12 according to an embodiment of theinvention.

According to some embodiments of the invention, the record generator 18generates an identifier 26 for the record 20 and an identifier 28 forthe link 24.

The record 20 has a structure similar to the instruction file 12according to some embodiments of the invention.

According to some embodiments of the invention, the record 20 includesnot limited to, at least one of a user identifier, an occurrence of thecheck-in event and an identifier of the at least one instruction file.The occurrence of the check-in event includes at least a date and atime.

According to some embodiments of the invention, the record generator 18registers a first check-out event when the first modification item isbeing check-out, registers a first check-in event when the firstmodification item is check-in. The record generator then compares thefirst modification item at the first check-in event and at the firstcheck-out event to determine if the first modification item is modified.

The record generator 18 generates a table 50 according to someembodiments of the invention. The table may include, but not limited to,identifiers 26 of the plurality of the records 20, identifiers 28 of theassociated links 24 and identifiers 52 of the associated instructionfiles 12.

According to some embodiments of the invention, at the check-in event,the link generator 22 is configured to determine if at least one of theplurality of modification items 14 which is being check-out is relatedto one modification item 14 in the record 20. Some modification items 14are related to each other and this detects if related modification items14 are not being check-in at the same check-in event. The link generator22 generates a notification when the at least one of the plurality ofmodification items 14 is related to the one modification item 14 in therecord and not being check-in. This alerts user that modification hasnot been completed.

FIG. 6A illustrates a workflow 600 of a method according to someembodiments of the invention.

In Step S602, the modification management system 100 identifies acheck-out event at a first time instance. In Step S604, the modificationmanagement system 100 identifies a check-in event at a second timeinstance. In Step S606, the comparator 16 determines if each of aplurality of modification items 14 in an instruction file 12 has beenmodified. In Step S608, the generator 18 is configured to create arecord 20 and stores the modification item 14 determines if each of theplurality of modification items 14 has been modified. In Step S610, thelink generator 22 is configured to generate a link 24 between the record20 and the instruction file 20 when the each of the plurality ofmodification items 14 has been modified.

FIG. 6B illustrates a workflow 620 of a method according to someembodiments of the invention when there is a plurality of instructionfiles and each instruction file has a plurality of modification items.In Step S622, the modification management system 100 identifies acheck-out event at a first time instance. In Step S624, the modificationmanagement system 100 identifies a check-in event at a second timeinstance. In Step S626, the comparator 16 determines if each of aplurality of modification items 14 in an instruction file 12 has beenmodified. In Step S628, the record generator 18 is configured to createa record 20 and stores the modification item 14 determines if each ofthe plurality of modification items 14 has been modified. In Step S630,the link generator 22 is further configured to identify the instructionfile for each of the plurality of modification items in the record 20.The link generator 22 generates a plurality of links 24 between therecord 20 and each of the plurality of instruction files 20 when morethan one instruction files has been identified.

Advantageously, the records 20 can be used to confirm if modificationitems 14 which are listed in an instruction file 12 have been completed.Efficiency, in terms of time and effort, which is required to identifyor confirm modifications in a configuration system. Multiplemodifications to a configuration system are easily traceable from thelinks 24 to identify the instruction files 12. Based on the instructionfiles 12, users can determine if the modification items 24 were modifiedcorrectly.

The systems and methods in the above-described embodiments may bedeployed in part or in whole through a machine or circuitry thatexecutes computer software, software components, program codes, and/orinstructions on one or more processors. The one or more processors maybe part of a general-purpose computer, a server, a cloud server, aclient, network infrastructure, mobile computing platform, stationarycomputing platform, or other computing platform. One or more processorsmay be any kind of computational or processing device or devices whichare capable of executing program instructions, codes, binaryinstructions and the like. The one or more processors may be or includea signal processor, digital processor, embedded processor,microprocessor or any variants such as a co-processor, for example, mathco-processor, graphic co-processor, communication co-processor and thelike that may directly or indirectly facilitate execution of programcodes or program instructions stored thereon. In addition, the one ormore processors may enable execution of multiple programs, threads, andcodes. The threads may be executed simultaneously to enhance theperformance of the one or more processors and to facilitate simultaneousoperations of the application. Program codes, program instructions andthe like described herein may be implemented in one or more threads. Theone or more processors may include memory that stores codes,instructions and programs as described herein. The processor may accessa non-transitory processor-readable storage medium through an interfacethat may store codes, instructions and programs as described herein andelsewhere. The non-transitory processor-readable storage mediumassociated with the processor for storing programs, codes, programinstructions or other type of instructions capable of being executed bythe computing or processing device may include but may not be limited toone or more of a memory, hard disk, flash drive, RAM, ROM, CD-ROM, DVD,cache and the like.

A processor may include one or more cores that may enhance speed andperformance of a multiprocessor. In some embodiments, the process may bea dual core processor, quad core processors, other chip-levelmultiprocessor and the like that combine two or more independent cores.

The methods and systems described herein may be deployed in part or inwhole through a machine that executes computer software on a server,client, firewall, gateway, hub, router, or other such computer and/ornetworking hardware.

The software program may be associated with one or more client that mayinclude a file client, print client, domain client, internet client,intranet client and other variants such as secondary client, hostclient, distributed client and the like. The client may include one ormore of memories, processors, computer readable media, storage media,physical and virtual ports, communication devices, and interfacescapable of accessing other clients, servers, machines, and devicesthrough a wired or a wireless medium, and the like. The programs orcodes as described herein may be executed by the client. In addition,other devices required for execution of methods as described in thisapplication may be considered as a part of the infrastructure associatedwith the client. The client may provide an interface to other devicesincluding servers, other clients, printers, database servers, printservers, file servers, communication servers, distributed servers andthe like. This coupling and/or connection may facilitate remoteexecution of program across the network. The networking of some or allof these devices may facilitate parallel processing of a program ormethod at one or more location. In addition, any of the devices attachedto the client through an interface may include at least one storagemedium capable of storing methods, programs, applications, code and/orinstructions. A central repository may provide program instructions tobe executed on different devices. In this implementation, the remoterepository may act as a storage medium for program code, instructions,and programs.

The software program may be associated with one or more servers that mayinclude a file server, print server, domain server, internet server,intranet server and other variants such as secondary server, hostserver, distributed server and the like. The server may include one ormore of memories, processors, computer readable media, storage media,physical and virtual ports, communication devices, and interfacescapable of accessing other servers, clients, machines, and devicesthrough a wired or a wireless medium, and the like. The methods,programs or codes as described herein may be executed by the server. Inaddition, other devices required for execution of methods as describedin this application may be considered as a part of the infrastructureassociated with the server. The server may provide an interface to otherdevices including clients, other servers, printers, database servers,print servers, file servers, communication servers, distributed servers,social networks, and the like. This coupling and/or connection mayfacilitate remote execution of program across the network. Thenetworking of some or all of these devices may facilitate parallelprocessing of a program or method at one or more locations. Any of thedevices attached to the server through an interface may include at leastone storage medium capable of storing programs, codes and/orinstructions. A central repository may provide program instructions tobe executed on different devices. In this implementation, the remoterepository may act as a storage medium for program codes, instructions,and programs.

The methods and systems described herein may be deployed in part or inwhole through network infrastructures. The network infrastructure mayinclude elements such as computing devices, servers, routers, hubs,firewalls, clients, personal computers, communication devices, routingdevices and other active and passive devices, modules and/or componentsas known in the art. The computing and/or non-computing devicesassociated with the network infrastructure may include, apart from othercomponents, a storage medium such as flash memory, buffer, stack, RAM,ROM and the like. The processes, methods, program codes, instructionsdescribed herein and elsewhere may be executed by one or more of thenetwork infrastructural elements.

The methods, program codes, and instructions described herein may beimplemented on a cellular network having multiple cells. The cellularnetwork may either be frequency division multiple access (FDMA) networkor code division multiple access (CDMA) network. The cellular networkmay include mobile devices, cell sites, base stations, repeaters,antennas, towers, and the like. The cell network may be a GSM, GPRS, 3G,EVDO, mesh, or other networks types.

The methods, programs codes, and instructions described herein andelsewhere may be implemented on or through mobile devices. The mobiledevices may include navigation devices, cell phones, mobile phones,mobile personal digital assistants, laptops, palmtops, netbooks, pagers,electronic books readers, music players and the like. These devices mayinclude, apart from other components, a storage medium such as a flashmemory, buffer, RAM, ROM and one or more computing devices. Thecomputing devices associated with mobile devices may be enabled toexecute program codes, methods, and instructions stored thereon.Alternatively, the mobile devices may be configured to executeinstructions in collaboration with other devices. The mobile devices maycommunicate with base stations interfaced with servers and configured toexecute program codes. The mobile devices may communicate on a peer topeer network, mesh network, or other communications network. The programcode may be stored on the storage medium associated with the server andexecuted by a computing device embedded within the server. The basestation may include a computing device and a storage medium. The storagedevice may store program codes and instructions executed by thecomputing devices associated with the base station.

The computer software, program codes, and/or instructions may be storedand/or accessed on machine readable media that may include: computercomponents, devices, and recording media that retain digital data usedfor computing for some interval of time; semiconductor storage known asrandom access memory (RAM); mass storage typically for more permanentstorage, such as optical discs, forms of magnetic storage like harddisks, tapes, drums, cards and other types; processor registers, cachememory, volatile memory, non-volatile memory; optical storage such asCD, DVD; removable media such as flash memory, for example, USB sticksor keys, floppy disks, magnetic tape, paper tape, punch cards,standalone RAM disks, Zip drives, removable mass storage, off-line, andthe like; other computer memory such as dynamic memory, static memory,read/write storage, mutable storage, read only, random access,sequential access, location addressable, file addressable, contentaddressable, network attached storage, storage area network, bar codes,magnetic ink, and the like.

The methods and systems described herein may transform physical and/oror intangible items from one state to another. The methods and systemsdescribed herein may also transform data representing physical and/orintangible items from one state to another.

The modules, engines, components, and elements described herein,including in flow charts and block diagrams throughout the figures,imply logical boundaries between the modules, engines, components, andelements. However, according to software or hardware engineeringpractices, the modules, engines, components, and elements and thefunctions thereof may be implemented on one or more processors,computers, machines through computer executable media, which are capableof executing program instructions stored thereon as a monolithicsoftware structure, as standalone software modules, or as modules thatemploy external routines, codes, services, or any combination of these,and all such implementations may be within the scope of the presentdisclosure. Examples of such machines may include, but is not limitedto, personal digital assistants, laptops, personal computers, mobilephones, other handheld computing devices, medical equipment, wired orwireless communication devices, transducers, chips, calculators,satellites, tablet PCs, electronic books, gadgets, electronic devices,devices having artificial intelligence, computing devices, networkingequipment, servers, routers, processor-embedded eyewear and the like.Furthermore, the modules, engines, components, and elements in the flowchart and block diagrams or any other logical component may beimplemented on one or more machines, computers or processors capable ofexecuting program instructions. Whereas the foregoing descriptions anddrawings to which the descriptions have been referred set forth somefunctional aspects of the disclosed systems, no particular arrangementof software for implementing these functional aspects should be inferredfrom these descriptions unless explicitly stated or otherwise clear fromthe context. It will also be appreciated that the various stepsidentified and described above may be varied, and that the order ofsteps may be adapted to particular applications of the techniquesdisclosed herein. All such variations and modifications are intended tofall within the scope of this disclosure. The descriptions of an orderfor various steps should not be understood to require a particular orderof execution for those steps, unless required by a particularapplication, or explicitly stated or otherwise clear from the context.

The methods and/or processes described above, and steps thereof, may berealized in hardware, software or any combination of hardware andsoftware suitable for a particular application. The hardware may includea general purpose computer and/or dedicated computing device or specificcomputing device or particular aspect or component of a specificcomputing device. The processes may be realized in one or moremicroprocessors, microcontrollers, embedded microcontrollers,programmable digital signal processors or other programmable device,along with internal and/or external memory. The processes may also, orinstead, be embodied in an application specific integrated circuit, aprogrammable gate array, programmable array logic, or any other deviceor combination of devices that may be configured to process electronicsignals. It will further be appreciated that one or more of theprocesses may be realized as a computer executable code capable of beingexecuted on a machine readable medium.

The computer executable code may be created using a structuredprogramming language such as C, an object oriented programming languagesuch as C++, or any other high-level or low-level programming language(including assembly languages, hardware description languages, anddatabase programming languages and technologies) that may be stored,compiled or interpreted to run on one of the above devices, as well asheterogeneous combinations of processors, processor architectures, orcombinations of different hardware and software, or any other machinecapable of executing program instructions.

Thus, in one aspect, each method described above and combinationsthereof may be embodied in computer executable code that, when executingon one or more computing devices, performs the steps thereof. In anotheraspect, the methods may be embodied in systems that perform the stepsthereof, and may be distributed across devices in a number of ways, orall of the functionality may be integrated into a dedicated, standalonedevice or other hardware. In another aspect, the means for performingthe steps associated with the processes described above may include anyof the hardware and/or software described above. All such permutationsand combinations are intended to fall within the scope of the presentdisclosure.

While the present disclosure includes many embodiments shown anddescribed in detail, various modifications and improvements thereon willbecome readily apparent to those skilled in the art. Accordingly, thespirit and scope of the present invention is not to be limited by theforegoing examples, but is to be understood in the broadest senseallowable by law.

We claim:
 1. A modification management system for a configurationsystem, comprising: a. a comparator configured to determine if a firstmodification item in the first instruction file is modified; b. a recordgenerator configured to create a first record and to store the firstmodification item in the first record when the first modification itemis determined, by the comparator, to be modified at; and c. a linkgenerator configured to generate a first link between the first recordand the first instruction file, wherein the first instruction file isconfigured to define at least one modification item for theconfiguration system, wherein the comparator, the record generator andthe link generator are implemented by circuitry or one or more hardwareprocessor with software components.
 2. The system in claim 1, wherein:the comparator is configured to determine if a second modification itemin one of the first instruction file and a second instruction file ismodified; the comparator is configured to create a second record and tostore the second modification item in the second record when the secondmodification item is determined, by the comparator, to be modified, thesecond record is different from the first record, wherein the secondinstruction file is configured to define at least one modification itemfor the configuration system; the link generator is further configuredto generate a second link between the second record and one of the firstinstruction file and the second instruction file, a part of which is themodification item.
 3. The system in claim 1, wherein the recordgenerator is configured to create at least one of a first recordidentifier for the first record and a first link identifier for thefirst link.
 4. The system in claim 1, wherein the link generator isconfigured to: determine if there is a third modification item isrelated to the first modification item and not in the first recordgenerate a notification when the third modification item is determinedto being related to the first modification item and not in the firstrecord.
 5. The system in claim 1, wherein the created first recordcomprises at least one of a user identifier, a date of the created firstrecord and an identifier of the at least one instruction file.
 6. Thesystem in claim 1, wherein: the comparator is configured to register afirst check-out event when the first modification item is check-out;register a first check-in event when the first modification item ischeck-in; and compare the first modification item at the first check-inevent and at the first check-out event to determine if the firstmodification item is modified.
 7. The system in claim 1, furthercomprising: a table configured to store an identifier of the recordfile; an identifier of an associated instruction file; and a identifierof an associated link between the record and the instruction file.
 8. Amodification management method for a configuration system, the methodcomprising a-1. determining if a first modification item in a firstinstruction file is modified; b-1. creating a first record when thefirst modification item is determined to be modified, c-1. storing thefirst modification item which is modified is stored in a first record;and d-1. generating a first link between the first record and the atleast one instruction file wherein the first instruction file isconfigured for the configuration system.
 9. The method in claim 8,further comprising: a-2. determining if a second modification item inone of the first instruction file and a second instruction file ismodified; b-2. creating a second record when the second modificationitem is determined to be modified the second record is different fromthe first record; c-2. storing the second modification item in thesecond record when the second modification item is determined to bemodified; d-2. generating a second link between the second record andone of the first instruction file and the second instruction file,wherein the second instruction file is configured for the processcontrol configuration system.
 10. The method in claim 8, furthercomprising at least one of creating a first record identifier for thefirst record and creating a first link identifier for the first link.11. The method in claim 8, further comprising: e. determining if a thirdmodification item is related to the first modification item and not inthe first record; and f. generating a notification when the thirdmodification item is determined to being related to the firstmodification item and not in the first record.
 12. The method in claim8, wherein the first record comprises at least one of a user identifier,a modification date and an identifier for the first instruction file.13. The method in claim 8, further comprising g. registering a firstcheck-out event when the first modification item is check-out; h.registering a first check-in event when the first modification item ischeck-in; and i. comparing the first modification item at the firstcheck-in event and at the first check-out event to determine if thefirst modification item is modified.
 14. A non-transitory computerreadable medium that stores a computer program to be executed by amodification management system to perform a modification managementmethod for a configuration system, the modification management methodcomprising: a-1. determining if a first modification item in a firstinstruction file is modified; b-1. creating a first record when thefirst modification item is determined to be modified, c-1. storing thefirst modification item which is modified is stored in a first record;and d-1. generating a first link between the first record and the atleast one instruction file wherein the first instruction file isconfigured for the configuration system.
 15. The medium in claim 14wherein the method further comprising: a-2. determining if a secondmodification item in one of the first instruction file and a secondinstruction file is modified; b-2. creating a second record when thesecond modification item is determined to be modified the second recordis different from the first record; c-2. storing the second modificationitem in the second record when the second modification item isdetermined to be modified; d-2. generating a second link between thesecond record and one of the first instruction file and the secondinstruction file, wherein the second instruction file is configured forthe process control configuration system.